GreenCityUser PR

Added brute-force protection to application.

• Integrated a new service to track and block accounts when a user enters incorrect credentials beyond the allowed number of attempts. This service helps to prevent brute-force attacks by monitoring and limiting login attempts.
• Implemented CAPTCHA validation to detect bots and prevent automated login attempts. If the CAPTCHA is invalid after a set number of tries, the account is blocked.
• Created an email template that will be sent to the user when their account is blocked, providing instructions on how to reset their password and unlock their account.
• Added unit tests to cover the brute-force protection functionality, including tracking, blocking, and unblocking logic.
• Introduced new environment variables to configure the maximum number of allowed attempts (maxAttempts) and the block duration (blockTime), allowing dynamic adjustment of security settings.
• Modified the signIn method to incorporate the new logic for checking account statuses and updating login attempts.

Issue Link 📋

#7583

PR Checklist Forms

(to be filled out by PR submitter)

• Code is up-to-date with the dev branch.
• You've successfully built and run the tests locally.
• There are new or updated unit tests validating the change.
• JIRA/ Github Issue number & title in PR title (ISSUE-XXXX: Ticket title)
• This template filled (above this section).
• Sonar's report does not contain bugs, vulnerabilities, security issues, code smells ar duplication
• NEED_REVIEW and READY_FOR_REVIEW labels are added.
• All files reviewed before sending to reviewers